build(deps-dev): bump wrangler from 4.120.0 to 4.123.0 - #1252

Sourced from wrangler's releases.

wrangler@4.123.0

Minor Changes

• #15113 b8fd112 Thanks @​BSFishy! - Add local dev simulation for Cloudflare Access ctx.access.getIdentity()

  You can now configure a mock Cloudflare Access identity in wrangler.json so that ctx.access.getIdentity() returns it during local development.

  // wrangler.json
  {
    "access": {
      "dev": {
        "aud": "my-app-aud-tag",
        "identity": {
          "email": "user@example.com",
          "name": "Test User"
        }
      }
    }
  }

• #15152 f0f2054 Thanks @​GregBrimble! - [private beta]: Updates the --ignore-defaults flag to --ignore-base-config on wrangler preview commands.

  --ignore-base-config now only takes effect on Preview creation, rather than on each deployment, since Preview base configuration is now copy-on-create rather than inherit-on-deploy.

• #14872 339509d Thanks @​dario-piotrowicz! - Add automatic update prompts for out-of-date Cloudflare agent skills

  When Cloudflare skills were previously installed by Wrangler and the upstream cloudflare/skills repository has newer content, Wrangler now offers to update them after eligible commands complete.

  To reduce prompt fatigue, the update check only runs once a month (30 days since the last install or update). Declining suppresses the prompt until the next upstream change.

  When declining an update, Wrangler offers the option to permanently disable future update prompts. This preference is stored globally in ~/.wrangler/agents-skills-install.jsonc. The WRANGLER_NO_SKILLS_UPDATE_PROMPTS=true environment variable can also be used to suppress prompts. The --install-skills flag remains available regardless of these settings.

Patch Changes

• Updated dependencies [b8fd112]:
  • miniflare@5.20260811.1-alpha

wrangler@4.122.0

Minor Changes

• #15123 d0c976c Thanks @​dependabot! - Detect Node.js compatibility from the compatibility date, now that nodejs_compat is enabled by default

  As of compatibility date 2026-08-04, workerd enables the nodejs_compat and nodejs_compat_v2 compatibility flags by default. Previously these tools only treated Node.js compatibility as enabled when one of those flags was listed explicitly, so a Worker on a compatibility date of 2026-08-04 or later without the flag would get Node.js APIs from the runtime but no Node.js polyfills from the bundler, and process.env could be substituted with an empty object at build time. They now resolve these flags the same way workerd does, and honour no_nodejs_compat to opt out.

  To keep Node.js compatibility switched off on a newer compatibility date, specify both no_nodejs_compat and no_nodejs_compat_v2, since each flag has its own default.

  @cloudflare/vitest-pool-workers needs nodejs_compat_v2 for its own test runner, so it continues to override a project that opts out of it. On a compatibility date that enables the flag anyway, it now drops the opt-out rather than adding the flag back, which workerd would reject — previously this stopped such a project from running any tests at all.

... (truncated)

• c576a82 Version Packages (#15154)
• 339509d Add automatic update prompts for out-of-date Cloudflare agent skills (#14872)
• b8fd112 feat: implement local dev for ctx.access (#15113)
• f0f2054 Replace ignore-defaults with ignore-base-config CLI arg for Previews (#15152)
• e5d56e9 Version Packages (#15145)
• 3b02915 [wrangler] Avoid stale remote binding sessions (#15142)
• d0c976c Bump the workerd-and-workers-types group across 1 directory with 2 updates (#...
• 15fc568 Version Packages (#15118)
• 5b1b930 Fetch script metadata directly instead of listing all scripts (#15132)
• 0aa8fa5 Support DO_NOT_TRACK=1 (#14924)
• Additional commits viewable in compare view